We use cookies on this website. To find out more about cookies and how they are used on this website, see our Privacy Policy.
By clicking ‘Continue’, you hereby agree with our use of cookies.

{{vmH.selected.familySearch.replace("EonStor ", "")}} Maintenance Guide

{{vmH.selected.familySearch.replace("EonStor ", "")}} User Guide

Maintenance Guide

Creating a Windows Virtual Machine

KS / KS 3000U / KSa 3004U

This section describes a typical workflow for creating a Windows virtual machine in IEC. For general VM configuration options, see Creating a Virtual Machine.

Overview

When creating a Windows VM, users configure the VM name, namespace, CPU, memory, storage, network, scheduling rules, and advanced options. Windows-specific setup usually requires additional attention to storage and network drivers, especially when VirtIO devices are used.

Unlike most Linux distributions, Windows does not include VirtIO drivers by default. If the VM uses VirtIO-based storage or network devices, the drivers must be loaded manually during installation.

Prerequisites

Before creating a Windows VM, verify the following:

  • A Windows operating system image has already been uploaded
  • The required namespace is available
  • Required storage resources are available
  • A VirtIO driver image is available if VirtIO devices will be used
  • RDP will be used later for remote access after guest installation is complete

Procedure

Step 1: Open the Virtual Machine Creation Page

  1. Go to EonKube > Virtualization > Virtual Machines.
  2. Click Create.

Step 2: Configure Basic Settings

In the Basic section, configure the following:

  • Namespace: Select the namespace where the VM will be created.
  • Name: Enter a name for the VM.
  • Description: Optional.

Configure the compute resources:

  • CPU: Allocate at least 2 cores for a basic Windows installation.
  • Memory: Allocate at least 4 GiB.
  • SSH Key: Leave this field blank
    Note:

    Windows does not support this function. To remotely manage a Windows VM, use Remote Desktop Protocol (RDP).

  • GPU: Optional. Configure GPU allocation only if required.

Step 3: Configure Disk/CD-ROM Settings

In the Disk/CD-ROM section, configure the VM storage layout.

  1. Select the Virtual Machine Image as the source disk.
  2. Configure the disk settings:
    • Name: For example, disk-0
    • Image: Select the uploaded Windows image, such as windows-10-22h2.iso
    • StorageClass: Select the required storage backend
    • Size: Specify the required disk size
    • Bus Type: Select VirtIO, SATA, or SCSI
      • If VirtIO is used, the required driver must be loaded during Windows installation.
      • If a VMDK image is used, SATA is generally recommended for compatibility.

If needed, add additional disks or CD-ROM devices:

  • Add Existing Disk
  • Add Disk
  • Add CD-ROM

If multiple bootable devices are present, adjust the boot order as needed.

Step 4: Configure Network Settings

In the Networks section, the system creates nic-0 by default as the primary network interface for pod network connectivity.

For the default interface nic-0:

  • The Name field is preset to nic-0
  • The Model field is preset to e1000
  • Only the MAC address can be configured manually

This default interface provides the Windows virtual machine with baseline connectivity to the Kubernetes environment.

If additional network connectivity is required, click Add Network to add another interface, such as nic-1. Additional interfaces can be used for secondary or bridged network access, depending on the environment and platform configuration.

For additional interfaces, users can typically configure:

  • Name
  • Model
  • MAC address

If virtio is selected for an additional interface, the required VirtIO network driver must be available to the guest operating system. Since Windows does not include VirtIO drivers by default, manual driver loading may be required during installation or after the VM is deployed.

Important!

For maximum compatibility during initial Windows installation, keep the default nic-0 configuration unless a different network design is specifically required.

Step 5: Configure Node Scheduling

In the Node Scheduling section, choose where the VM can run. Available options include:

  • Run on any available node
  • Run on a specific node
  • Run on nodes matching scheduling rules

If node selection rules are required:

  1. Click Add Node Selector.
  2. Select Required or Preferred.
  3. Add one or more rules.
  4. Save the scheduling configuration.

Step 6: Configure Advanced Options

In the Advanced Options section, configure the Linux-specific runtime options. Recommended settings:

  • OS Type: Select Windows
  • Run Strategy: Select the appropriate option for the workload
  • Hostname: Optional. By default, the hostname follows the VM name
  • Enable USB Tablet: Keep enabled if VNC access will be used
  • Install Guest Agent: Recommended
  • Booting in EFI Mode: Enabled by default
  • Secure Boot: Optional

Cloud configuration and network data are not supported for Windows in this workflow.

Step 7: Create the VM

  1. Review the complete configuration.
  2. Click Create.

The creation process may take several minutes.

Installing Windows and Loading Drivers

After the VM is created, continue the guest OS installation.

  1. Open the VM console from EonKube > Virtualization > Virtual Machines.
  2. Select Open in Web VNC.
  3. Start the Windows installation process.

If Windows does not detect the target disk or network interface:

  1. Click Browse during the installation process.
  2. Locate the mounted VirtIO driver media.
  3. Select the appropriate Windows driver.
  4. Load the driver.
  5. Continue the installation.

After the installation is complete:

  1. Sign in to Windows.
  2. Open Device Manager.
  3. Confirm that all required devices are recognized correctly.
  4. Install any additional drivers if unknown devices remain.

After the VM Is Created

After Windows installation is complete:

  1. Verify network connectivity.
  2. Confirm that required drivers are installed.
  3. Enable or verify Remote Desktop Protocol (RDP) access if needed.
  4. Connect remotely by using the VM IP address and valid guest credentials.
Note:
  • Windows does not support SSH key injection in this workflow.
  • If VirtIO devices are used, manual driver loading is usually required during setup.
  • RDP is the recommended method for ongoing remote administration.
  • Additional CPU, memory, and storage may be required depending on the Windows edition and workload.